Hey Lalit! The idea for this issue is to add documentation to the reference. This is done by writing JSDoc comments which get pulled in when the p5.js website is built and reference pages are generated. Look here for the contributor guidelines for JS Doc:
https://github.com/processing/p5.js/blob/dev-2.0/contributor_docs/jsdoc.md

Once you've put this code into a JSDoc comment, commit and push the results, and then run the command npm run custom:dev your-branch-url in the p5.js-website repo again to build the site with the updated changes. You will have to clone the website repository here. This way you can also preview your documentation in the reference and make sure it all looks good there.

Oh also in #7849 (comment) I was mentioning those uniforms as things that would be good to have as built-in nodes, so they don't need to be manually added to reference examples. So for those you'd probably need to modify the ShaderGenerator.js file like you were doing for noise and lerp.

Hi! While testing the changes locally using npm run custom:dev your-branch-url in the p5.js-website repo, I encountered schema validation errors in some .mdx tutorial files like:

• tutorials/en/loading-and-selecting-fonts.mdx
• tutorials/en/getting-started-with-nodejs.mdx

Just to clarify, I haven’t edited these files, the errors appeared during preview and seem unrelated to my PR. Thought I’d flag it here in case it's helpful. Thanks!

Hi! While testing the changes locally using npm run custom:dev your-branch-url in the p5.js-website repo, I encountered schema validation errors in some .mdx tutorial files like:

* `tutorials/en/loading-and-selecting-fonts.mdx`

* `tutorials/en/getting-started-with-nodejs.mdx`

Just to clarify, I haven’t edited these files, the errors appeared during preview and seem unrelated to my PR. Thought I’d flag it here in case it's helpful. Thanks!

Do you mind checking with the 2.0 branch of p5.js-website? That should probably work for you,
https://github.com/processing/p5.js-website/tree/2.0

Sorry, for the late response and also thanks for your patience and great work so far! :)

Hi @LalitNarayanYadav I wanted to check in here as well. Are you still working on this PR? Please ping in the next week (no need to be finished by then, just to confirm you're still on it) - otherwise we can finish it up. Thank you!

Hi @ksen0,
Thanks for checking in. I’m sorry for the delay in updates. I got caught up with my internship, college, and project work, so I couldn’t give this PR the attention it needed. I still wanted to work on it, but if the timeline is tight, I completely understand if someone else takes it forward.